Collapse All Expand All

Use the following steps to install PrizmDoc in a Linux headless environment:

 

Step 1 - Download PrizmDoc

Before downloading PrizmDoc, you will need to purchase a license key or request a Trial Evaluation by filling out the following form: www.accusoft.com/products/prizm-content-connect-pcc/get-self-hosted/.

Once you have purchased a license key or filled out the form for a Trial Evaluation, you can download PrizmDoc by:

1. Following the link provided in the response email and selecting the desired Linux Distribution.

OR

2. Downloading directly to the Linux server using the 'wget' command for the specific distribution as shown below:

You must substitute the version of the package you are using in the code examples below. For example, if you are using v11.0, then specify "11.0" instead of "<version>". If the version is a hot fix, you will need to also specify the hot fix number, for example, "11.0.1".

   

Red Hat, Fedora, CentOS, and Older Linux Distributions

Example	Copy Code
wget http://products.accusoft.com/PrizmDoc/<version>/prizmdoc_full_<version>.x86_64.rpm.tar.gz

Debian and Ubuntu Linux Distributions

Example	Copy Code
wget http://products.accusoft.com/PrizmDoc/<version>/prizmdoc_full_<version>.amd64.deb.tar.gz

Generic .tar.gz Distribution

Example	Copy Code
wget http://products.accusoft.com/PrizmDoc/<version>/prizmdoc_full_<version>.x86_64.tar.gz

For license, fill out the form at http://www.accusoft.com/products/prizm-content-connect-pcc/get-self-hosted/ or http://www.accusoft.com/contact/. 

Step 2 - Unpack & Install the Downloaded Archive

Open a command line and change to the location where you downloaded the tarball. Use the following command line examples appropriate for your distribution to:

1. Decompress and unpack the downloaded file. After you have unpacked the archive, the contents will have been decompressed into a directory named prizmdoc_full_<version>.<arch>[.rpm|.deb]. 
2. Change to the unpacked directory and install the packages.

Red Hat, Fedora, CentOS, and Older Linux Distributions

The following example is for Red Hat, Fedora, CentOS, and older Linux distributions:

Example	Copy Code
tar -xzvf prizmdoc_full_*.rpm.tar.gz cd prizmdoc_full_*.rpm yum install -nogpgcheck *.rpm

Note: For CentOS 5.x, the following additional dependencies must be installed prior to PrizmDoc RPM installation: openjpeg-libs-1.3-7.el5.x86_64.rpm pixman-0.22.0-2.2.el5_10.x86_64.rpm The Prizm installer does not install them automatically. Please manually download these packages and then install them using --nogpgcheck flag as follows: Example Copy Code yum install --nogpgcheck ./openjpeg-libs-1.3-7.el5.x86_64.rpm yum install --nogpgcheck ./pixman-0.22.0-2.2.el5_10.x86_64.rpm

Debian (Ubuntu) Linux Distributions

The following example is for Debian (Ubuntu) Linux distributions:

Example	Copy Code
tar -xzvf prizmdoc_full_*.deb.tar.gz cd prizmdoc_full_*.deb sudo dpkg -i *.deb sudo apt-get -f install

Generic .tar.gz Distribution

We also provide a generic .tar.gz package. You will need to install the dependencies described in the Requirements section. Once the dependencies are installed, you can install the .tar.gz with the following commands as root:

Example	Copy Code
tar -xzvf prizmdoc_full*.tar.gz cd prizmdoc_full_* ls prizm-*.tar.gz | xargs -n1 tar zxf cp -R prizm /usr/share/

 

Step 3 - Setup

1. Run the following commands to initiate setup:

Example	Copy Code
cd /usr/share/prizm sh ./setup.sh

The setup script will now invoke a text-based wizard for licensing:

To install a license at the end of the evaluation period, (for example, a deployment license), run the following command: Example Copy Code ./setup.sh eval get youremail@example.com If you already have a license for PrizmDoc, you can use one of the other licensing options, detailed in the Command Line Mode Licensing section of the help.

2.  To confirm the licensing has succeeded, run the following command, which will output your license key:   

Example	Copy Code
cat ./conf/proxyserver_jar.properties | grep license_key > license_key=<long string>

       

3. If PrizmDoc has started and no errors have been reported, then the installation process is complete.

However, if you have an error in the log stating that it cannot connect to the Office converter Worker-1 instance, then you must continue to the 'Step 4 - Running an X Virtual Framebuffer' section below.

 

Step 4 - Running an X Virtual Framebuffer Server

A full version of the X11 server is not required to run PrizmDoc. However, the minimum requirement is the X Virtual Framebuffer Server, which you can install and run separately from an entire X11 instance.

1. To install the X Virtual Framebuffer Server, run the following command:

Debian/Ubuntu

Example	Copy Code
sudo apt-get install xvfb

   

Red Hat / CentOS

Example	Copy Code
yum install xorg-x11-server-Xvfb

2. Start the service by running the following command, and then export the instance to the DISPLAY environment variable expected by the PrizmDoc Server:

Example	Copy Code
Xvfb :20 >/dev/null 2>&1 & export DISPLAY=:20

3. Start PrizmDoc:

Example	Copy Code
/usr/share/prizm/scripts/pccis.sh start

Required:

The X Virtual Framebuffer Server must be running any time that the PrizmDoc Server is running.

Suggested:

It may be appropriate to create a script that will start the Xvfb service and PrizmDoc Server (the 3 lines above) to execute whenever the machine is restarted. 

 

Step 5 - Verify that the Installation was Successful   

1. Browse to the following either via URL or through browser http://localhost:18681/admin:

 

It may take several minutes for PrizmDoc Server to become completely healthy. The page will auto-refresh as PrizmDoc Server come online.

2. Your installation is now complete. 

 

Enabling Upload of Larger Files

By default /usr/share/prizm/pccis/servicehost/host.config contains the following limitation:

Example	Copy Code
/usr/share/prizm/pccis/servicehost/host.config "httpRuntime": { ... "maxRequestLength": 50000000 }

which limits maximum document file size to 50Mb, and so PCCIS will return HTTP-500 when larger files are uploaded to the service. If you are dealing with larger files it will necessary to change the "maxRequestLength" option to a more appropriate value. 

 

 

---

©2016. Accusoft Corporation. All Rights Reserved.

Send Feedback